Published 2008-08-24 23:32:33

Just a small update on roojs1 - I've added in-line comments to the RooJs1 documentation - so if you think a method or class is not well explained, add your comment, example code, or bug note right on the documentation. - Something I think makes a huge difference to the usability of code...

Other small changes are also beginning to be added - including the fields property of a Roo.toolbar, and the new Roo.form.Hidden element, to make creating forms with hidden variables simpler.

Anyway, rumors are swirling around that there is a recommendation to avoid ExtJS among certain linux distributors due to uncertainties and general lack of confidence in the license, it's continual changing and general poor behavior by Jack in not understanding the implications of the bait and switch changes.

It also appears that Jack's Legal team are working harder than his coding team again, sending out threatening letters to people involved in various ExtJs2 derivative works. (which is the key reason I'm focusing on v1 - clear, definitive separation and licenses that do not allow for such shenanigans)

While ExtJS2 offered some interesting new features. The significant change to the object rendering model, from my experience has been broken on every release prior to the GPL one, (and since I never tested it after that release, I suspect it's still broken).

Other changes relating to a clearer heirachy of object model look like they should be a simple addition to ExtJS1, along with better support for non DOM element dependent constructors. Hence I think building on ExtJS1 appears to be a better long term move, and sounds like a few more are beginning to see that wisdom.

Mentioned By:
www.planet-php.net : Planet PHP (43 referals)
google.com : php inline if (39 referals)
google.com : december (30 referals)
google.com : inline if php (13 referals)
www.cnzxh.net : CNZXH.NET 关注基于Linux的开源应用 - In-line comments on RooJS1 docs - More nails in ExtJs coffin - Alan Knowles (6 referals)
google.com : php inline comment (5 referals)
google.com : php comment line (4 referals)
www.geexoo.com : PHP - All Latest Feeds from Top Blogs for PHP (3 referals)
google.com : comment lines in php (3 referals)
google.com : extjs (3 referals)
google.com : in-line comments (3 referals)
google.com : november (3 referals)
google.com : php inline comments (3 referals)
google.com : php line comment (3 referals)
google.com : comment line for php 5 (2 referals)
google.com : comment line in php (2 referals)
google.com : inline comments (2 referals)
google.com : inline comments code (2 referals)
google.com : php in line if (2 referals)
google.com : php in-line comments (2 referals)

Comments

Safari Weirdness
There is something really weird going on with the the doc comment stuff in Safari, I can't even quite explain it. But, very cool (in FF) anyhow :)

- Davey
#0 - Davey Shafik ( Link) on 2008-08-25 02:06:10 Delete Comment
Safari Support
I've fixed the main issues for Safari (well Konq) - it has serious issues with rendering and scoping, so the main iframe has to be hidden when you are entering the comment.

There is also a bug that calling parent.* for any of the Roo stuff in Konqueror looses the ability to do stuff like instanceof Array (known bug of Konqueror)

Anyway there are still CSS issues for Konqueror - so if any one wants to send the fixes.. just add a comment to combobox etc.
#1 - Alan Knowles ( Link) on 2008-08-25 15:14:10 Delete Comment
Impressive
I think I will start migrating some of my code from extjs to roojs with all these improvements.
#2 - Herman Radtke ( Link) on 2008-08-31 03:24:54 Delete Comment
re: css MIME types
uncertain whether the author is aware, but this is what Google Chrome had to say about one of the resources had to say (a hasty perusal, btw-- apologies for i did not investigate further). Note, this not to point out so much of roojs (aside from friendly "hey, did you notice that the...), as to remark upon [what i found to be, at least] a relatively unique perspective on web resource evaluation. (i.e. I wonder if this would also catch dynamic CSS, if an author were to leave out the header ( css mime stuff ) part. blah, blah. the picture is worth more than my thousand words. apologies all 'round. i shut up now...
http://picasaweb.google.com/novicenotes/MiscellaneousSharedItems#5248878014852876658
#3 - NoviceNotes ( Link) on 2008-09-23 00:18:35 Delete Comment
css Mime isses
these where 404 pages - so I guess google chrome is showing the wrong messages...

Anyway some of the examples have missing css/gif files, which are pretty trivial and not really essential. so I've just commented them out for the time being.
#4 - Alan Knowles ( Link) on 2008-09-23 07:47:20 Delete Comment

Add Your Comment